feat(rules): New Potential NTLM hash leak via MS Photos rule#559
Open
rabbitstack wants to merge 1 commit intomasterfrom
Open
feat(rules): New Potential NTLM hash leak via MS Photos rule#559rabbitstack wants to merge 1 commit intomasterfrom
Potential NTLM hash leak via MS Photos rule#559rabbitstack wants to merge 1 commit intomasterfrom
Conversation
rabbitstack
force-pushed
the
ntlm-leak-via-ms-photos
branch
from
22451a5 to
60b39cc
Compare
Detects a potential NTLM hash disclosure via abuse of the ms-photos: URIscheme with a UNC path parameter. An attacker can craft a specially formatted link that, when opened, launches Microsoft Photos directly from a browser and triggers outbound authentication, potentially leaking NTLM credentials.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of this PR / why it is needed?
Identifies a potential NTLM hash leak via ms-photos URI scheme parameter which can be submitted with UNC path. Adversaries can craft a specially formatted link and coerce a victim into launching the Microsoft Photos directly from the browser.
What type of change does this PR introduce?
/kind feature (non-breaking change which adds functionality)
Any specific area of the project related to this PR?
/area rules
Special notes for the reviewer
Does this PR introduce a user-facing change?